Technology companies are starting to respond to a new Wi-Fi exploit affecting Vulnerability-related.DiscoverVulnerability all modern Wi-Fi networks using WPA or WPA2 encryption . The security vulnerabilities allow attackers to read Wi-Fi traffic between devices and wireless access points , and in some cases even modify it to inject malware into websites . Security researchers claim Vulnerability-related.DiscoverVulnerability devices running macOS , Windows , iOS , Android , and Linux will be affected Vulnerability-related.DiscoverVulnerability by the vulnerabilities . Microsoft says it has already fixed Vulnerability-related.PatchVulnerability the problem for customers running supported versions of Windows . “ We have released Vulnerability-related.PatchVulnerability a security update to address Vulnerability-related.PatchVulnerability this issue , ” says a Microsoft spokesperson in a statement to The Verge . “ Customers who apply Vulnerability-related.PatchVulnerability the update , or have automatic updates enabled , will be protected . We continue to encourage customers to turn on automatic updates to help ensure they are protected. ” Microsoft says the Windows updates released Vulnerability-related.PatchVulnerability on October 10th protect customers , and the company “ withheld disclosure Vulnerability-related.DiscoverVulnerability until other vendors could develop and release Vulnerability-related.PatchVulnerability updates. ” While it looks like Android and Linux devices are affected Vulnerability-related.DiscoverVulnerability by the worst part of the vulnerabilities , allowing attackers to manipulate websites , Google has promised Vulnerability-related.PatchVulnerability a fix for affected devices “ in the coming weeks. ” Google ’ s own Pixel devices will be the first to receive Vulnerability-related.PatchVulnerability fixes with security patch level of November 6 , 2017 , but most other handsets are still well behind even the latest updates . Security researchers claim Vulnerability-related.DiscoverVulnerability 41 percent of Android devices are vulnerable Vulnerability-related.DiscoverVulnerability to an “ exceptionally devastating ” variant of the Wi-Fi attack that involves manipulating traffic , and it will take time to patch Vulnerability-related.PatchVulnerability older devices . The Verge has reached out to a variety of Android phone makers to clarify when security patches will reach Vulnerability-related.PatchVulnerability handsets , and we ’ ll update you accordingly . At the time of writing , Apple has not yet clarified Vulnerability-related.DiscoverVulnerability whether the latest versions of macOS and iOS are vulnerable Vulnerability-related.DiscoverVulnerability . The Wi-Fi Alliance , a network of companies responsible for Wi-Fi , has responded to the disclosure Vulnerability-related.DiscoverVulnerability of the vulnerabilities . “ This issue can be resolved Vulnerability-related.PatchVulnerability through straightforward software updates , and the Wi-Fi industry , including major platform providers , has already started deploying Vulnerability-related.PatchVulnerability patches to Wi-Fi users , ” says a Wi-Fi Alliance spokesperson . “ Users can expect all their Wi-Fi devices , whether patched or unpatched Vulnerability-related.PatchVulnerability , to continue working well together. ” Apple also confirmed to both The Verge and AppleInsider that the vulnerability is patched Vulnerability-related.PatchVulnerability in a beta version of the current operating systems . The fix should go public Vulnerability-related.PatchVulnerability in a few weeks , so iOS and macOS devices are n't in the clear just yet . AppleInsider also reports that AirPort hardware , including the Time Machine , AirPort Extreme base station , and AirPort Express do not have a patch . The publication 's source also was n't sure if one was in the works .

A Russian vulnerability researcher and exploit developer has published Vulnerability-related.DiscoverVulnerability detailed information about a zero-day vulnerability in VirtualBox . His explanations include step-by-step instructions for exploiting the bug . According to the initial details in the disclosure Vulnerability-related.DiscoverVulnerability , the issue is present Vulnerability-related.DiscoverVulnerability in a shared code base of the virtualization software , available on all supported operating systems . Exploiting Vulnerability-related.DiscoverVulnerability the vulnerability allows an attacker to escape the virtual environment of the guest machine and reach the Ring 3 privilege layer , used for running code from most user programs , with the least privileges . Turning one `` overflow '' into another Sergey Zelenyuk found Vulnerability-related.DiscoverVulnerability that the security bug can be leveraged on virtual machines configured with the Intel PRO/1000 MT Desktop ( 82540EM ) network adapter in Network Address Translation ( NAT ) mode , the default setup that allows the guest system to access external networks . `` The [ Intel PRO/1000 MT Desktop ( 82540EM ) ] has a vulnerability allowing an attacker with root/administrator privileges in a guest to escape to a host ring3 . Then the attacker can use existing techniques to escalate privileges to ring 0 via /dev/vboxdrv , '' Zelenyuk writes Vulnerability-related.DiscoverVulnerability in a technical write-up on Tuesday . Zelenyuk says that an important aspect in getting how the vulnerability works is to understand that context descriptors are processed before data descriptors . The researcher describes the mechanics behind the security flaw in detail , showing how to trigger the necessary conditions to obtain a buffer overflow that could be abused to escape the confinements of the virtual operating system . First , he caused an integer underflow condition using packet descriptors - data segments that allow the network adapter to track network packet data in the system memory . This state was then leveraged to read data from the guest OS to into a heap buffer and cause an overflow condition that could lead to overwriting function pointers ; or to cause a stack overflow condition .

Microsoft has quickly reacted to the disclosure Vulnerability-related.DiscoverVulnerability of a previously unknown zero-day vulnerability in the Windows operating system . On Monday , Twitter user SandboxEscaper revealed Vulnerability-related.DiscoverVulnerability the existence of the bug on the microblogging platform . As reported by the Register , the user said : `` Here is the alpc bug as 0day . I do n't f * * king care about life anymore . Neither do I ever again want to submit to MSFT anyway . F * * k all of this shit . '' The user linked to a page on GitHub which appears to contain a proof-of-concept ( PoC ) for the vulnerability . Following the disclosure Vulnerability-related.DiscoverVulnerability , on Tuesday , Will Dormann , vulnerability analyst at CERT/CC verified Vulnerability-related.DiscoverVulnerability the bug , adding that the zero-day flaw works `` well in a fully-patched 64-bit Windows 10 system Vulnerability-related.PatchVulnerability . '' The Windows vulnerability is described as Vulnerability-related.DiscoverVulnerability a local privilege escalation security flaw in the Microsoft Windows task scheduler caused by errors in the handling of Advanced Local Procedure Call ( ALPC ) systems . If exploited Vulnerability-related.DiscoverVulnerability , the zero-day bug permits local users to obtain system privileges . As ALPC is a local system , the impact is limited , but the public disclosure Vulnerability-related.DiscoverVulnerability of a zero-day is still likely a headache for the Redmond giant . There are no known workarounds for the vulnerability , which has been awarded a CVSS score of 6.4 -- 6.8 . SandboxEscaper 's tweet has since been deleted . However , Microsoft has acknowledged Vulnerability-related.DiscoverVulnerability the zero-day flaw . This is likely to take place Vulnerability-related.PatchVulnerability on September 11 , the next scheduled Microsoft Patch Tuesday , unless the firm decides to issue Vulnerability-related.PatchVulnerability an out-of-schedule patch . `` Windows has a customer commitment to investigate reported security issues , and proactively update impacted devices as soon as possible . Our standard policy is to provide solutions via our current Update Tuesday schedule . ''

Microsoft has quickly reacted to the disclosure Vulnerability-related.DiscoverVulnerability of a previously unknown zero-day vulnerability in the Windows operating system . On Monday , Twitter user SandboxEscaper revealed Vulnerability-related.DiscoverVulnerability the existence of the bug on the microblogging platform . As reported by the Register , the user said : `` Here is the alpc bug as 0day . I do n't f * * king care about life anymore . Neither do I ever again want to submit to MSFT anyway . F * * k all of this shit . '' The user linked to a page on GitHub which appears to contain a proof-of-concept ( PoC ) for the vulnerability . Following the disclosure Vulnerability-related.DiscoverVulnerability , on Tuesday , Will Dormann , vulnerability analyst at CERT/CC verified Vulnerability-related.DiscoverVulnerability the bug , adding that the zero-day flaw works `` well in a fully-patched 64-bit Windows 10 system Vulnerability-related.PatchVulnerability . '' The Windows vulnerability is described as Vulnerability-related.DiscoverVulnerability a local privilege escalation security flaw in the Microsoft Windows task scheduler caused by errors in the handling of Advanced Local Procedure Call ( ALPC ) systems . If exploited Vulnerability-related.DiscoverVulnerability , the zero-day bug permits local users to obtain system privileges . As ALPC is a local system , the impact is limited , but the public disclosure Vulnerability-related.DiscoverVulnerability of a zero-day is still likely a headache for the Redmond giant . There are no known workarounds for the vulnerability , which has been awarded a CVSS score of 6.4 -- 6.8 . SandboxEscaper 's tweet has since been deleted . However , Microsoft has acknowledged Vulnerability-related.DiscoverVulnerability the zero-day flaw . This is likely to take place Vulnerability-related.PatchVulnerability on September 11 , the next scheduled Microsoft Patch Tuesday , unless the firm decides to issue Vulnerability-related.PatchVulnerability an out-of-schedule patch . `` Windows has a customer commitment to investigate reported security issues , and proactively update impacted devices as soon as possible . Our standard policy is to provide solutions via our current Update Tuesday schedule . ''

A popular version of the open source Magento ecommerce platform is vulnerable Vulnerability-related.DiscoverVulnerability to a zero-day remote code execution vulnerability , putting as many as 200,000 online retailers at risk . The warning comes from security firm DefenseCode , which found Vulnerability-related.DiscoverVulnerability and originally reported Vulnerability-related.DiscoverVulnerability the vulnerability to Magento in November . “ During the security audit of Magento Community Edition , a high risk vulnerability was discovered Vulnerability-related.DiscoverVulnerability that could lead to remote code execution and thus the complete system compromise including the database containing sensitive customer information such as stored credit card numbers and other payment information , ” DefenseCode wrote in a technical description of its discovery ( PDF ) posted Wednesday . According Bosko Stankovic , information security engineer at DefenseCode , despite repeated efforts to notify Vulnerability-related.DiscoverVulnerability Magento , which began in November 2016 , the vulnerability remains unpatched Vulnerability-related.PatchVulnerability despite four version updates since the disclosure Vulnerability-related.DiscoverVulnerability . DefenseCode did not examine Magento Enterprise , the commercial version of the platform , but warns both share the same underlying vulnerable code . “ We ’ re unsure if this vulnerability is actively being exploited Vulnerability-related.DiscoverVulnerability in the wild , but since the vulnerability has been unpatched Vulnerability-related.PatchVulnerability for so long it provides a window of opportunity for potential hackers , ” Stankovic said . Magento confirmed the existence Vulnerability-related.DiscoverVulnerability of the flaw in a brief statement to Threatpost and said it was investigating . “ We have been actively investigating Vulnerability-related.DiscoverVulnerability the root cause of the reported issue and are not aware of any attacks in the wild . We will be addressing Vulnerability-related.PatchVulnerability the issue in our next patch release and continue to consistently work to improve our assurance processes , ” Magento said in a statement . Yesterday , Threatpost reported Vulnerability-related.DiscoverVulnerability a story about a remote code execution vulnerability with Magento 2 Enterprise and Community software . Magento is committed to delivering superior security to clients and has been actively investigating Vulnerability-related.DiscoverVulnerability the root cause of the reported issue . We are not aware of any attacks in the wild . Admin access is required to execute the exploit , so as always , we encourage you to follow best practices to keep your Admin secure . In addition , this vulnerability will be addressed Vulnerability-related.PatchVulnerability in our next release Vulnerability-related.PatchVulnerability targeted for early May . Until then , we recommend enforcing the use of “ Add Secret Key to URLs ” to mitigate potential attacks .

Independent security researcher Dawid Golunski has released Vulnerability-related.DiscoverVulnerability a proof-of-concept exploit code for an unauthenticated remote code execution vulnerability in WordPress 4.6 ( CVE-2016-10033 ) , and information about an unauthorized password reset zero-day vulnerability ( CVE-2017-8295 ) in the latest version of the popular CMS . The vulnerability exists in Vulnerability-related.DiscoverVulnerability the PHPMailer library , and can be exploited Vulnerability-related.DiscoverVulnerability by unauthenticated remote attackers to gain access to and compromise an target application server on which a vulnerable WordPress Core version is installed ( in its default configuration ) . “ No plugins or non-standard settings are required to exploit the vulnerability , ” Golunski noted . The hole has been responsibly disclosed Vulnerability-related.DiscoverVulnerability to the WordPress Foundation , and has been plugged Vulnerability-related.PatchVulnerability in January , with the release of WordPress 4.7.1 . Still , according to the Foundation ’ s own numbers , nearly 11 percent of all WordPress installation out there are still stuck on the vulnerable version 4.6 . And , as Golunski noted Vulnerability-related.DiscoverVulnerability , it ’ s possible that older WordPress versions are also affected Vulnerability-related.DiscoverVulnerability by the same flaw , so the percentage of vulnerable installations could be considerably higher : Admins who still run these older versions of the popular CMS should upgrade Vulnerability-related.PatchVulnerability to newer versions , ideally to the latest one ( v4.7.4 ) . Still , even that might not be a guarantee against compromise , as Golunski has also publicly released Vulnerability-related.DiscoverVulnerability information and POC code for an unauthorized password reset vulnerability ( CVE-2017-8295 ) that the WordPress Foundation is yet to patch Vulnerability-related.PatchVulnerability . According to him and BeyondSecurity , whose SecuriTeam coordinated the disclosure Vulnerability-related.DiscoverVulnerability of the flaw to the WordPress developers , the discovery Vulnerability-related.DiscoverVulnerability of the vulnerability dates back to mid-2016 . Golunski found Vulnerability-related.DiscoverVulnerability it in version 4.3.1 of the CMS . “ WordPress has a password reset feature that contains Vulnerability-related.DiscoverVulnerability a vulnerability which might in some cases allow attackers to get hold of the password reset link without previous authentication . Such attack could lead to an attacker gaining unauthorized access to a victim ’ s WordPress account , ” BeyondSecurity explained . “ The vulnerability stems from WordPress using untrusted data by default when creating a password reset e-mail that is supposed to be delivered only to the e-mail associated with the owner ’ s account. ” Golunski says Vulnerability-related.DiscoverVulnerability that the issue was reported Vulnerability-related.DiscoverVulnerability to the WordPress security team multiple times , but they did not confirm whether it has been patched Vulnerability-related.PatchVulnerability . He ultimately decided to publish Vulnerability-related.DiscoverVulnerability his findings , and offer Vulnerability-related.PatchVulnerability a temporary solution ( “ users can enable UseCanonicalName to enforce static SERVER_NAME value ” ) .

A longtime Debian developer has recommended Vulnerability-related.DiscoverVulnerability that the Cryptkeeper Linux encryption app be removed from the distribution . The advice came after the disclosure Vulnerability-related.DiscoverVulnerability of a bug where the app sets the universal password “ p ” to decrypt any directory created with the program . Simon McVittie , a programmer at Collabora , confirmed the findings Vulnerability-related.DiscoverVulnerability of researcher Kirill Tkhai , who disclosed Vulnerability-related.DiscoverVulnerability the bug Jan. 26 . McVittie said Vulnerability-related.DiscoverVulnerability he was able to reproduce the bug in the Stretch version ( Debian 9 , in testing ) , but not in the Jessie version ( Debian 8 ) . “ I have recommended that the release team remove this package from stretch : it currently gives a false sense of security that is worse than not encrypting at all , ” McVittie said in response Vulnerability-related.DiscoverVulnerability to the original bug report . Francesco Namuri , another Debian developer , agreed the Cryptkeeper packages should be yanked from Debian . Tkhai ’ s advisory said Cryptkeeper version 0.9.5-5.1 is affected . The problem appears when Cryptkeeper calls encfs , a command line interface for the encrypted file system . Encfs simulates a ‘ p ’ keystroke but the uses it instead as a universal password .